feat(frontend): add i18n support for Yoruba, Igbo, and Hausa - #190
feat(frontend): add i18n support for Yoruba, Igbo, and Hausa#190annieolivia61-ux wants to merge 1 commit into
Conversation
|
@annieolivia61-ux Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
dark-sarge
left a comment
dark-sarge
left a comment
There was a problem hiding this comment.
please resolve all conflicts
- Install and configure next-intl with locales en, yo, ig, ha - Add URL-based locale prefixing (as-needed) via the i18n middleware - Create translation catalogs under frontend/locales/[locale]/common.json - Add a language switcher to the Navbar with cookie persistence - Replace hardcoded strings with translation keys across home, auth, wallet, and trade pages Closes arflexx#68
2a03d03 to
a8d39b5
Compare
|
@dark-sarge all conflicts resolved - I rebased the branch onto the latest main and re-merged every file (layout, profile, trades detail, wallet, withdraw modal, next.config.js, package.json, pnpm-lock.yaml). Key merges:
Verified locally:ext build - passes (all 15 routes compile, middleware included)
Note: several CI checks (Frontend (Next.js), Server (TypeScript), Trivy, Frontend CI lint) currently fail identically on the main branch (e.g. setup-node cache references nonexistent package-lock.json, and |
2 participants
Closes #68
What changed
next-intlwith localesen,yo,ig,ha.frontend/locales/[locale]/common.jsonfor home, auth, wallet, and trade pages./yo/wallet; defaultenhas no prefix).Navbar, persisting the choice in theNEXT_LOCALEcookie.How to test
cd frontend && pnpm exec next buildpnpm exec jest